Intelligent Roaming and Interworking

ABSTRACT

A mobile device may be configured with multiple access point names (APNs) including a roaming APN and a non-roaming APN. After a mobile device determines whether it is roaming, it may transmit a service request with the corresponding APN. The network may then select a profile based on the APN that may include quality of service parameters and other parameters for servicing the mobile device. The profile may be obtained from a local home location register or a remote home location register.

TECHNICAL FIELD

The technical field generally relates to wireless communications andmore specifically relates to roaming and interworking.

BACKGROUND

Wireless communications devices are often configured for use on both ahome network and, when roaming outside the coverage area of a homenetwork, a visiting network. The types of service and quality of servicethat are provided to a device that is roaming are not currentlydifferentiated based on any information specific to, or received from,the roaming device. Therefore, visiting networks are not able to adjusttheir service offerings to roaming users, for example, in order tobetter accommodate their own users. There is also not an efficient wayfor a home network to determine that its users are currently roaming.These and other deficiencies of the current state of the art areaddressed by the subject matter set forth herein.

SUMMARY

In an embodiment, a mobile device may be configured with two or moreaccess point names (APNs), each of which may be intended for use witheither a home network or a visiting network. The mobile device mayreceive a query from a wireless network for identifying information andmay transmit a network code to the wireless network. In an embodiment,the network code may be a mobile network code and a mobile country code(MNC+MCC). The mobile device may receive an indication of its roamingstatus from the wireless network and select an APN based on the mobiledevice's roaming status. In an embodiment, the mobile device may alsoreceive a confirmation that that the mobile device is eligible to usethe wireless network. The mobile device may transmit a service requestincluding the selected access point name the wireless network. Thewireless network may locate a profile based on the received APN. Theprofile may contain parameters to be used in providing communicationsservices to the mobile device. The wireless network may providecommunications services to the mobile device based on the parameters.

In an embodiment, a network device may detect a mobile device within thecoverage area of a network, send a query to the mobile device requestingmobile device identifying information, and receive mobile deviceidentifying information from the mobile device. The mobile deviceidentifying information maybe an MNC+MCC. The network device maydetermine, based on the mobile device identifying information, whetherthe mobile device is permitted to communicate with the network and aroaming status for the mobile device. The network device may transmitthe roaming status to the mobile device and, in an embodiment, aconfirmation that the mobile device is permitted to use the network. Thenetwork device may receive a service request that includes an accesspoint name from the mobile device and may determine service parametersbased on the access point name. Service parameters may be determining byobtaining a profile, or data from a profile, from a home locationregister (HLR). The HLR may be local to the network of the networkdevice, or it may be remote, for example, an HLR in the home network ofthe mobile device where the network of the network device is a visitingnetwork for the mobile device. The network device may establish acommunications link with the mobile device and provide communicationsservices to the mobile device based on the service parameters.

In an embodiment, a network device such as an HLR may receive a requestfor service parameters, where the request includes an access point name.The HLR may determine an access point name profile based on the accesspoint name. This may be accomplished by querying a local database.Alternatively, the HLR may transmit a query to a second HLR that may belocated in a different network and may receive an access point nameprofile, or a subset of data contained therein, from the second HLR. TheHLR may store the access point name profile or profile data receivedfrom the second HLR for future use. The HLR may retrieve the serviceparameters from the access point name profile and provide them to thedevice that requested them so that the requesting device can providecommunications services to a mobile device associated with the accesspoint name. These and other aspects of the present disclosure aredescribed in more detail herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The following detailed description of preferred embodiments is betterunderstood when read in conjunction with the appended drawings. For thepurposes of illustration, there is shown in the drawings exemplaryembodiments; however, the subject matter is not limited to the specificelements and instrumentalities disclosed. In the drawings:

FIG. 1A is a system diagram of an example communications system in whichone or more disclosed embodiments may be implemented.

FIG. 1B is a system diagram of an example mobile device (also referredto as a wireless transmit/receive unit (WTRU) and/or as user equipment(UE)) that may be used within the communications system illustrated inFIG. 1A.

FIG. 1C is a system diagram of an example radio access network and anexample core network that may be used within the communications systemillustrated in FIG. 1A.

FIG. 2A illustrates a non-limiting exemplary network configuration for adevice communicating with its home network according to an embodiment.

FIG. 2B illustrates a non-limiting exemplary network configuration for adevice communicating with a visiting network according to an embodiment.

FIG. 3 illustrates a non-limiting exemplary signal flow according to anembodiment.

FIG. 4 illustrates a non-limiting exemplary method of implementing anembodiment.

FIG. 5 illustrates another non-limiting exemplary method of implementingan embodiment.

FIG. 6 illustrates a non-limiting exemplary network configuration for adevice communicating with a visiting network and a home networkaccording to an embodiment.

FIG. 7 illustrates another non-limiting exemplary signal flow accordingto an embodiment.

FIG. 8 illustrates another non-limiting exemplary method of implementingan embodiment.

FIG. 9 is a block diagram of a non-limiting exemplary mobile device inwhich intelligent roaming and interworking may be implemented.

FIG. 10 is a block diagram of a non-limiting exemplary processor inwhich intelligent roaming and interworking may be implemented.

FIG. 11 is a block diagram of an non-limiting exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichintelligent roaming and interworking may be implemented.

FIG. 12 illustrates a non-limiting exemplary architecture of a typicalGPRS network, segmented into four groups, in which intelligent roamingand interworking may be implemented.

FIG. 13 illustrates a non-limiting alternate block diagram of anexemplary GSM/GPRS/IP multimedia network architecture in whichintelligent roaming and interworking may be implemented.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

FIG. 1A is a diagram of an example communications system 100 in whichone or more disclosed embodiments may be implemented. The communicationssystem 100 may be a multiple access system that provides content, suchas voice, data, video, messaging, broadcast, etc., to multiple wirelessusers. The communications system 100 may enable multiple wireless usersto access such content through the sharing of system resources,including wireless bandwidth. For example, the communications systems100 may employ one or more channel access methods, such as code divisionmultiple access (CDMA), time division multiple access (TDMA), frequencydivision multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrierFDMA (SC-FDMA), and the like. A communications system such as that shownin FIG. 1A may also be referred to herein as a network.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a radioaccess network (RAN) 104, a core network 106, a public switchedtelephone network (PSTN) 108, the Internet 110, and other networks 112,though it will be appreciated that the disclosed embodiments contemplateany number of WTRUs, base stations, networks, and/or network elements.Each of the WTRUs 102 a, 102 b, 102 c, 102 d may be any type of deviceconfigured to operate and/or communicate in a wireless environment. Byway of example, the WTRUs 102 a, 102 b, 102 c, 102 d may be configuredto transmit and/or receive wireless signals and may include userequipment (UE), a mobile station, a mobile device, a fixed or mobilesubscriber unit, a pager, a cellular telephone, a personal digitalassistant (PDA), a smartphone, a laptop, a netbook, a personal computer,a wireless sensor, consumer electronics, and the like.

The communications systems 100 may also include a base station 114 a anda base station 114 b. Each of the base stations 114 a, 114 b may be anytype of device configured to wirelessly interface with at least one ofthe WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to one or morecommunication networks, such as the core network 106, the Internet 110,and/or the networks 112. By way of example, the base stations 114 a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a HomeNode B, a Home eNode B, a site controller, an access point (AP), awireless router, and the like. While the base stations 114 a, 114 b areeach depicted as a single element, it will be appreciated that the basestations 114 a, 114 b may include any number of interconnected basestations and/or network elements.

The base station 114 a may be part of the RAN 104, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals within aparticular geographic region, which may be referred to as a cell (notshown). The cell may further be divided into cell sectors. For example,the cell associated with the base station 114 a may be divided intothree sectors. Thus, in an embodiment, the base station 114 a mayinclude three transceivers, i.e., one for each sector of the cell. Inanother embodiment, the base station 114 a may employ multiple-inputmultiple output (MIMO) technology and, therefore, may utilize multipletransceivers for each sector of the cell.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, infrared (IR), ultraviolet (UV), visible light, etc.). Theair interface 116 may be established using any suitable radio accesstechnology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104 and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish the air interface 116 using wideband CDMA (WCDMA). WCDMAmay include communication protocols such as High-Speed Packet Access(HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed DownlinkPacket Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114 a and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish the air interface116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.16 (i.e.,Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000,CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), InterimStandard 95 (IS-95), Interim Standard 856 (IS-856), Global System forMobile communications (GSM), Enhanced Data rates for GSM Evolution(EDGE), GSM EDGE (GERAN), and the like.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, and the like. In oneembodiment, the base station 114 b and the WTRUs 102 c, 102 d mayimplement a radio technology such as IEEE 802.11 to establish a wirelesslocal area network (WLAN). In another embodiment, the base station 114 band the WTRUs 102 c, 102 d may implement a radio technology such as IEEE802.15 to establish a wireless personal area network (WPAN). In yetanother embodiment, the base station 114 b and the WTRUs 102 c, 102 dmay utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 1A,the base station 114 b may have a direct connection to the Internet 110.Thus, the base station 114 b may not be required to access the Internet110 via the core network 106.

The RAN 104 may be in communication with the core network 106, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. For example, the core network 106may provide call control, billing services, mobile location-basedservices, pre-paid calling, Internet connectivity, video distribution,etc., and/or perform high-level security functions, such as userauthentication. Although not shown in FIG. 1A, it will be appreciatedthat the RAN 104 and/or the core network 106 may be in direct orindirect communication with other RANs that employ the same RAT as theRAN 104 or a different RAT. For example, in addition to being connectedto the RAN 104, which may be utilizing an E-UTRA radio technology, thecore network 106 may also be in communication with another RAN (notshown) employing a GSM radio technology.

The core network 106 may also serve as a gateway for the WTRUs 102 a,102 b, 102 c, 102 d to access the PSTN 108, the Internet 110, and/orother networks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) andthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired or wireless communications networks ownedand/or operated by other service providers. For example, the networks112 may include another core network connected to one or more RANs,which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities, i.e., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks. For example, the WTRU 102 c shown in FIG. 1A may be configured tocommunicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram of an example WTRU 102. As shown in FIG. 1B,the WTRU 102 may include a processor 118, a transceiver 120, atransmit/receive element 122, a speaker/microphone 124, a keypad 126, adisplay/touchpad 128, non-removable memory 130, removable memory 132, apower source 134, a global positioning system (GPS) chipset 136, andother peripherals 138. It will be appreciated that the WTRU 102 mayinclude any sub-combination of the foregoing elements while remainingconsistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In another embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and receive both RF and light signals. It will be appreciatedthat the transmit/receive element 122 may be configured to transmitand/or receive any combination of wireless signals.

In addition, although the transmit/receive element 122 is depicted inFIG. 1B as a single element, the WTRU 102 may include any number oftransmit/receive elements 122. More specifically, the WTRU 102 mayemploy MIMO technology. Thus, in one embodiment, the WTRU 102 mayinclude two or more transmit/receive elements 122 (e.g., multipleantennas) for transmitting and receiving wireless signals over the airinterface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, and the like.

FIG. 1C is a system diagram of the RAN 104 and the core network 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the core network 106.

The RAN 104 may include eNode-Bs 140 a, 140 b, 140 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 140 a, 140 b, 140c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 140 a, 140 b, 140 c may implement MIMO technology. Thus,the eNode-B 140 a, for example, may use multiple antennas to transmitwireless signals to, and receive wireless signals from, the WTRU 102 a.

Each of the eNode-Bs 140 a, 140 b, 140 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the uplink and/or downlink, and the like. As shown in FIG. 1C, theeNode-Bs 140 a, 140 b, 140 c may communicate with one another over an X2interface.

The core network 106 shown in FIG. 1C may include a mobility managementgateway (MME) 142, a serving gateway 144, and a packet data network(PDN) gateway 146. While each of the foregoing elements are depicted aspart of the core network 106, it will be appreciated that any one ofthese elements may be owned and/or operated by an entity other than thecore network operator.

The MME 142 may be connected to each of the eNode-Bs 142 a, 142 b, 142 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 142 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 142 may also provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

The serving gateway 144 may be connected to each of the eNode Bs 140 a,140 b, 140 c in the RAN 104 via the S1 interface. The serving gateway144 may generally route and forward user data packets to/from the WTRUs102 a, 102 b, 102 c. The serving gateway 144 may also perform otherfunctions, such as anchoring user planes during inter-eNode B handovers,triggering paging when downlink data is available for the WTRUs 102 a,102 b, 102 c, managing and storing contexts of the WTRUs 102 a, 102 b,102 c, and the like.

The serving gateway 144 may also be connected to the PDN gateway 146,which may provide the WTRUs 102 a, 102 b, 102 c with access topacket-switched networks, such as the Internet 110, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and IP-enableddevices.

The core network 106 may facilitate communications with other networks.For example, the core network 106 may provide the WTRUs 102 a, 102 b,102 c with access to circuit-switched networks, such as the PSTN 108, tofacilitate communications between the WTRUs 102 a, 102 b, 102 c andtraditional land-line communications devices. For example, the corenetwork 106 may include, or may communicate with, an IP gateway (e.g.,an IP multimedia subsystem (IMS) server) that serves as an interfacebetween the core network 106 and the PSTN 108. In addition, the corenetwork 106 may provide the WTRUs 102 a, 102 b, 102 c with access to thenetworks 112, which may include other wired or wireless networks thatare owned and/or operated by other service providers.

In wireless communications systems, including those described herein andothers, various means and methods may be used to identify a mobiledevice (referred to herein interchangeably as a wirelesstransmit/receive unit (WTRU) and user equipment (UE)) and determinewhether that mobile device is roaming, or otherwise communicating with anetwork that is not its home network. The network with which a roamingdevice is communicating may be referred to as a visiting network. Thirdgeneration mobile telecommunications systems (commonly referred to as“3G”) may use a single Serving GPRS Support Node (SGSN) IP Address toidentify a roaming mobile device on a visiting network. A visiting SGSN(V-SGSN) may receive, store, and send the IP address and/or otheridentifying information associated with the roaming mobile device to ahome gateway GPRS support node (H-GGSN) in the mobile device's homenetwork, thereby informing the home network that the mobile device isroaming on the visiting network. The information sent to an H-GGSN inthe mobile device's home network may include a radio bearer indicator(RBI), location information, and other roaming information. Upon receiptof such information, the home network may query a home location register(HLR) in the home network to determine if the mobile device is eligiblefor roaming service and provide the result of that determination to thevisiting network. If the mobile device is eligible for roaming service,the visiting network may permit the mobile device to activate one ormore packet data protocol (PDP) contexts with the V-SGSN in order tofacilitate communications via the visiting network. Since suchembodiments use a single SGSN IP address for the mobile device, the sametypes and qualities of service are provided to the mobile device whetherit is roaming or on its home network

In another example, a mobile device configured to operate on one or moreLTE networks may be identified by a single access point name (APN)configured on the mobile device that may be referred to as a PHONE APN.An APN may include a network identifier, an operator identifier, and/ora service identifier identifying a service requested by the mobiledevice. The mobile device's PHONE APN may be used to set up a defaultbearer path in the visiting network (also referred to a visiting publicland mobile network or V-PLMN) to provide roaming communicationsservices to the mobile device. The PHONE APN may also be used todetermine the types and levels of service that the mobile device is toreceive. Since such embodiments use a single APN for the mobile device,the same types and levels of service are provided to the mobile devicewhether it is roaming or on its home network (also referred to a homepublic land mobile network or H-PLMN). In such an embodiment, the homenetwork of the mobile device may not be aware of whether the mobiledevice is roaming or not.

It may be desirable, however, to provide different types and/or levelsof service to a mobile device depending on whether the mobile device isroaming and without involving a device such as an SGSN to determinewhether a device is roaming. Therefore, in an embodiment a mobile devicemay be configured with two or more APNs, with at least one for use inroaming and at least one for use in the home network. FIGS. 2A and 2Billustrate exemplary, non-limiting network configurations for suchembodiments.

In FIG. 2A, mobile device 210 may be configured with APNs 220. Mobiledevice 210, and all mobile devices described herein, may be any type ofmobile communications device, including a UE or WTRU capable ofoperating on one or more LTE networks or any other communicationsnetwork of any type. APNs 220 may include PHONE APN 230 and ROAM APN240. When in a coverage area of home network 201, mobile device 210 mayprovide PHONE APN 230 to home network 201 to identify itself, set up oneor more bearer paths, and may otherwise use PHONE APN 230 incommunications with home network 201. Note that mobile device 210, andany mobile device described herein, may communicate directly with anynetwork element or device in a radio access network, including, but notlimited to, a base station and an eNode-B. In an embodiment, mobiledevice 210 may determine whether home network 201 is a home network or avisiting network by any means, including receiving a roaming indicationfrom home network 201, detecting a radio bearer of home network 201,and/or determining a network identity from a radio bearer. Home network201 may determine, directly or indirectly, the service types andqualities permitted to mobile device 210 based on the PHONE APN and/orone or more profiles associated with PHONE APN as described in moredetail herein. In an embodiment, home network 201 may obtain the servicetypes and qualities permitted to mobile device 210 from HLR 250 that maybe located within and/or communicatively connected to home network 201.

In FIG. 2B, mobile device 210 is also configured with APNs 220 that mayinclude PHONE APN 230 and ROAM APN 240. Here, mobile device 210 may havedetermined that visiting network 202 is a visiting network by any means,including receiving a roaming indication from visiting network 202,detecting a radio bearer of visiting network 202, and/or determining anetwork identity from a radio bearer. Upon such a determination, mobiledevice 210 may use ROAM APN 240 to identify itself, set up one or morebearer paths, and may otherwise use ROAM APN 240 in communications withvisiting network 202. Visiting network 202 may determine, directly orindirectly, the service types and qualities permitted to mobile device210 based on the ROAM APN and/or one or more profiles associated withROAM APN as described in more detail herein. In an embodiment, visitingnetwork 202 may obtain the service types and qualities permitted tomobile device 210 from visiting network HLR 260 that may be locatedwithin and/or communicatively connected to visiting network 202. HLR 260may obtain service types and qualities permitted to mobile device 210from an HLR associated with the home network of mobile device 210, suchas HLR 270 that may be communicatively connected to visiting network 202via, for example, home network 201. Alternatively, visiting network 202may obtain the service types and qualities permitted to mobile device210 from home network HLR 270 that may be communicatively connected tovisiting network 202 via, for example, home network 201, or may belocated within and/or communicatively connected to visiting network 202.

FIG. 3 illustrates exemplary non-limiting signal flows that may be usedaccording to an embodiment. In the illustrated embodiment, mobile device310 may be in a coverage area serviced by network 320. Network 320 maybe a home network or a visiting network. Note that, as used herein,“network 320” may refer to the entirety of network 320, any networkdevice within network 320, any component of network 320, or anycombination thereof. Upon detection of mobile device 310, at signal 331network 320 may query mobile device 310 to obtain information thatnetwork 320 may use to determine whether the device is eligible to usenetwork 320. Such a query may be specifically for device identifyinginformation, such as mobile device 310's mobile network code (MNC) andmobile country code (MCC) that when taken together (MNC+MCC) provide aunique identifier for a carrier or communications provider associatedwith mobile device 210. At signal 332, mobile device 310 may transmitits MNC+MCC to network 320. Note that any alternate or additionalidentifying information is contemplated, as is other methods and meansof determining whether mobile device 310 is eligible to use network 320.

Network 320 may evaluate the received MNC+MCC or alternate informationand determine that mobile device 310 is eligible to use network 320.Network 320 may also use the received MNC+MCC and/or other informationto determine whether mobile device 310 is roaming, i.e., whether network320 is a home network (e.g., received MNC+MCC corresponds to orotherwise identifies network 320) or a visiting network (e.g., receivedMNC+MCC does not correspond to or otherwise identify network 320) formobile device 310. Network 320 may transmit signal 333 to mobile device310 indicating that mobile device 310 is eligible to use network 320and/or whether mobile device 310 is roaming.

If the roaming status received in signal 333 indicates that mobiledevice 310 is roaming, mobile device 310 may select a ROAM APNconfigured in mobile device 310. Alternatively, if the roaming statusreceived in signal 333 indicates that mobile device 310 is not roaming,mobile device 310 may select a PHONE APN configured in mobile device310. Mobile device 310 may then transmit a service request to initiateone or more bearer paths to network 320 that includes the selected APN.The selected APN may be appended to the service request or otherwiseincluded in the service request.

At signal 335, mobile device 310 and network 320 may exchange anyinformation necessary to set up one or more bearer paths, and, in anembodiment, network 320 may determine bearer path parameters and otherparameters based on information determined at least in part on the APNprovided in signal 334. At signal 336, network resources may be used toprovide service to mobile device 310. In an embodiment, the provisionand use of such network resources may be based on parameters and otherdata obtained, at least in part, on the APN provided in signal 334. Thetype and quality of service provided may be those that mobile device 310is eligible to receive based on a profile associated with the APNprovided in signal 334. Embodiments that network 320 may use todetermine the type and quality of service are described in more detailherein.

FIG. 4 illustrates an exemplary method 400 that may be performed by amobile device in an embodiment. Note that the activities and functionsdescribed in regard to method 400 and any other method disclosed hereinmay be performed in any order, and any subset of such activities andfunctions may be performed in any embodiment without requiring theperformance of any other activities or functions disclosed herein. Notealso that additional activities and functions may be combined and/orperformed with the any of the disclosed activities and functions and allsuch embodiments are contemplated as within the scope of the presentdisclosure.

At block 405, a mobile device may receive a query from a networkproviding coverage to an area in which the mobile device is currentlylocated. The query may be a query for any identifying information,including, but not limited to, an MNC+MCC configured on the mobiledevice. At block 410, the mobile device may transmit its MNC+MCC to thequerying network. Alternatively, at block 410 the mobile device maytransmit any other identifying information or any other type of responseto the querying network. At block 415, the mobile device may receive itsroaming status from the network. Any other information may be receivedfrom the network at block 415, including a confirmation that the mobiledevice is permitted to use the network.

At block 420, the mobile device may determine whether the mobile deviceis roaming or not (i.e., whether the network currently providingcoverage is a home network or a visiting network) based on theinformation received at block 415. If the mobile device is not roaming,at block 425 the mobile device may transmit a service request includinga PHONE APN configured on the mobile device to the network. If themobile device is roaming, at block 430 the mobile device may transmit aservice request including a ROAM APN configured on the mobile device tothe network. Either service request may be a request to establish abearer path with the network in order to facilitate any type ofcommunications between the network and the mobile device. Whether themobile device is roaming or not, at block 435 the mobile device may takeany actions and transmit and/or receive any communications that may beused to establish a bearer path between the mobile device and thenetwork. The network resources that are allocated for the mobile devicemay be determined by the network based on the roaming status of themobile device and/or on the APN provided by the mobile device to thenetwork, as described in more detail herein.

FIG. 5 illustrates an exemplary method 500 that may be performed by anetwork, or any of one or more devices within a network, according to anembodiment. At block 505, a network may query a mobile device detectedwithin its coverage area for information that may allow the network todetermine if the mobile device is permitted to establish communicationswith the network and/or if the mobile device is roaming or not (i.e.,whether the network is a home network or a visiting network for themobile device.) The query may be a query for any identifyinginformation, including, but not limited to, an MNC+MCC configured on themobile device. At block 510, the network may receive a MNC+MCC from themobile device. Alternatively, at block 510 the network may receive anyother identifying information or any other type of response from themobile device. At block 515, the network may determine the roamingstatus of the mobile device based on MNC+MCC. For example, the networkmay determine whether the carrier or communications provider associatedwith the MNC+MCC is the operator of the network (thus indicating thatthe network is a home network for the mobile device) or a carrier orcommunications provider associated with the MNC+MCC is a carrier orcommunications provider that has an established roaming agreement withthe network (thus indicating that the network is a visiting network forthe mobile device and the mobile device is permitted to roam on thenetwork.) The roaming status of the mobile device, and any otherinformation such as a confirmation that the mobile device is permittedto use the network, may be transmitted to the mobile device at block515. Any other information may be transmitted to the mobile device atblock 515.

At block 520, the network may receive a service request from the mobiledevice that includes an APN that, in an embodiment, may be either aPHONE APN or a ROAM APN. At block 525, the network may query an HLR,providing the HLR with the APN, to determine the network resources,services, and quality of service (QoS) to be provided to the mobiledevice. In an embodiment, the network may be a home network and may havereceived a PHONE APN from the mobile device at block 520. In such anembodiment, the HLR queried may be an HLR within the network.Alternatively, the network may be a visiting network and may havereceived a ROAM APN from the mobile device at block 520. In such anembodiment, the network may query an HLR in the mobile device's homenetwork by sending a query directly to an HLR in the home network.Alternatively, the network may query one or more of its own HLRs. Inthis embodiment, one or more of the network's HLRs may have stored aprofile for the mobile device or a profile that can be used for themobile device that is associated with the APN provided to the network bythe mobile device. Alternatively, one or more of the network's HLRs may,upon receiving a query from the network, transmit a query to an HLR ofthe mobile device's home network and retrieve the network resources,services, and QoS to be provided to the mobile device. Such an HLR maystore these network resources, services, and QoS to be provided to themobile device for use in the future when the mobile device may againattempt to connect to the network.

Note that the network need not be aware of a type of the APN (e.g.,PHONE APN or ROAM APN) received from a mobile device, for example atblock 520. While the network may be aware of the roaming status of themobile device based on the received MNC+MCC or other information, theroaming status may not be used to determine the network resources,services, and QoS to be provided to the mobile device. Rather, thenetwork may use the APN received from the mobile device to obtain aprofile for the mobile device that contains the network resources,services, and QoS to be provided to the mobile device. Each APNconfigured on the mobile device may be associated with a distinctprofile, as described in more detail herein.

At block 530, the network may establish a bearer path with the mobiledevice, and at block 535, the network may provide services to the mobiledevice in accordance with the network resources, services, and QoSdetermined for the mobile device.

FIG. 6 illustrates an exemplary, non-limiting network environment inwhich an embodiment of the present disclosure may be implemented. Mobiledevice 610 may communicate with home network 601 when in home network601's coverage area 611. Mobile device 610 may be configured with APNs620 that may include PHONE APN 630 and ROAM APN 640. When mobile device610 determines that it is communicating with home network 601, it maytransmit a service request including PHONE APN 630 to home network 601.Home network 601 may then query home network HLR 650 for the networkresources, services, and QoS that are to be used for the communicationslink with mobile device 610. The query sent to home network HLR 650 mayinclude PHONE APN 630 provided to home network 601 in the servicerequest transmitted by mobile device 610.

Upon receiving the query, home network HLR 650 may perform a databaselook-up or otherwise determine that profile 671 is associated with PHONEAPN 630. Home network HLR 650 may then provide the associated QoSparameters, services, and priorities that home network 601 is to use inproviding communications services to mobile device 610. Home network 601may provide communications services to mobile device 610 based on theseQoS parameters, services, and priorities.

When mobile device 610 is in coverage area 612 of visiting network 602,mobile device 610 may transmit a service request including ROAM APN 640to visiting network 602. Visiting network 602 may then query visitingnetwork HLR 660 for the network resources, services, and QoS that are tobe used for the communications link with mobile device 610. The querysent to visiting network HLR 660 may include ROAM APN 640 provided tovisiting network 602 in the service request transmitted by mobile device610. Visiting network HLR 660 may transmit query 681 for networkresources, services, and QoS parameters to home network HLR 650. Query681 may include ROAM APN 640 as provided to visiting network 602 in theservice request transmitted by mobile device 610. Home network HLR 650may perform a database look-up or otherwise determine that profile 672is associated with ROAM APN 640. Home network HLR 650 may then providethe associated QoS parameters, services, priorities, and/or any otherinformation that may be used to establish and provide communicationsservices that visiting network 602 is to use in providing communicationsservices to mobile device 610 in response 682. Visiting network HLR 660may provide such communications services information to visiting network602 that may set up and provide communications services to mobile device610 using the received communications services information.

In an embodiment, visiting network HLR 660 may store the received QoSparameters, services, and priorities and/or other communicationsservices information for use in servicing further service requests frommobile device 610, thereby reducing network resource usage in the futureshould mobile device 610 again attempt to communicate with visitingnetwork 602. Alternatively, visiting network HLR 660 may obtain APNprofiles in advance from home network HLR 650 or from any other deviceassociated with home network 601. For example, upon establishing aroaming agreement between home network 601 and visiting network 602,devices within these networks may be configured to maintain current APNprofiles so that they can more expediently service roaming devices. Anyother means or methods of determining an APN profile, or elementsthereof, may be used and are contemplated as within the scope of thepresent disclosure.

Note that upon receiving a request for an APN profile from visitingnetwork HLR 660, home network HLR 650 may record or otherwise store anindication that mobile device 610 is currently roaming. Such anindication may include a date and time indicating when mobile device 610is roaming, the network on which mobile device 610 is roaming, and anyother information that may be used for any purpose by home network 601.

APN profiles may contain any data and/or parameters that may be used toprovide service to a mobile device. Such parameters and data may includedata rates, QoS parameters, priorities for various traffic types, timesand/or dates when certain parameters are to be used, etc.

FIG. 7 illustrates exemplary non-limiting method 700 that may beperformed by a home network HLR or another network device according toan embodiment. At block 705, the home network HLR may receive a queryfor QoS parameters, services, priorities, and/or any other informationthat may be used by a network to facilitate communications with a mobiledevice. The query may include an APN that has been provided to the homenetwork. This query may come from a device within the home networkitself, for example when attempting to establish a bearer path for andprovide communications services to a mobile device within the mobiledevice's home network coverage area. Alternatively, this query may bereceived from a device in a visiting network that is attempting toprovide roaming communications service to a mobile that is within thecoverage area of the visiting network.

At block 710, the home network HLR may determine a profile associatedwith the received APN. This may be accomplished using any means,including a database look-up based on the APN. At block 715, the homenetwork HLR may provide the profile in its entirety, the data within theprofile, or a subset of the data within the profile to the device thattransmitted the query.

FIG. 8 illustrates exemplary non-limiting method 800 that may beperformed by a visiting network HLR or another network device accordingto an embodiment. At block 805, the visiting network HLR may receive aquery from the visiting network for QoS parameters, services,priorities, and/or any other information that may be used by a networkto facilitate communications with a mobile device. The query may includean APN that has been provided to the visiting network. At block 810, thevisiting network HLR may determine whether it has a stored APN profileassociated with the received APN. For example, the visiting network HLRmay have previously received one or more APN profiles from a homenetwork HLR or other device and stored them If it does, at block 830 thevisiting network HLR may transmit the profile associated with thereceived APN in its entirety, the data within the profile, or a subsetof the data within the profile to the visiting network device thattransmitted the query.

If the visiting network HLR does not have a profile associated with thereceived APN, at block 815 the visiting network HLR may transmit arequest for APN profile data to a home network HLR associated with thehome network of the mobile device. The visiting network HLR maydetermine the home network from the APN, which may include a networkidentifier and/or an operator identifier. Alternatively, the visitingnetwork HLR may determine the home network from an MNC+MCC that themobile device may have provided, and which may have been transmitted tothe visiting network HLR with the query received at block 805. Any othermeans and methods of determining a home network and/or a home networkHLR for the purposes of retrieving APN profile data is contemplated aswithin the scope of the present disclosure.

A response to the request for APN profile data may be received at block820. The response may contain any data that may be used to provideservice to a roaming device, including, but not limited to, QoSparameters, services, and priorities. At block 825, the profile and/or asubset of data associated therewith may be stored by the visitingnetwork HLR for use in the future. At block 830, the visiting networkHLR may transmit the profile associated with the received APN in itsentirety, the data within the profile, or a subset of the data withinthe profile to the visiting network device that transmitted the query.

Note that APNs as described herein may each be unique and configured fora single device. For example, each mobile device configured according toan embodiment of the present disclosure may have a single unique APN forroaming (ROAM APN) and a single unique APN for communication with a homenetwork (PHONE APN). Thus, there may be one profile for each unique APN.Alternatively, the APNs configured on mobile devices may be moregeneral. For example, a carrier may provide one PHONE APN and one ROAMAPN for use by all or a plurality of its customers' devices. In anotheralternative, each mobile device may have more than one ROAM APN and/ormore than one PHONE APN. For example, a device may have one APN perparticular service that the device may request, such as one data accessAPN for roaming, one data access APN for use with a home network, onevoice APN for roaming, and/or one voice APN for use with a home network.Alternatively, or in addition, APNs may be used according to when aservice request is generated. For example, a mobile device may select afirst PHONE APN when communicating with a home network during one timeperiod during the day, and a second PHONE APN when communicating withthe home network during a different time period during the day. In anembodiment, one section of an APN may be used to indicate roaming orhome network communications. For example, part of the operatoridentifier may be reserved for indicating roaming status. Alternatively,codes within an APN may be used to indicate roaming status that arecarrier specific. For example, one carrier may use one APN format withcodes that indicate roaming status while another carrier may use adifferent format and/or codes for APNs that indicate roaming status. Anycombination of these and all other variations of APN configurations arecontemplated as within the scope of the present disclosure.

Note also that the APN profiles as described herein may be dynamic. Forexample, an HLR may adjust the data within an APN profile based oncertain criteria, such as time of day, time of week, current networktraffic loads, resources used by the mobile device associated with theAPN profile, user requests for alteration of the APN profile, etc.

The methods and systems described above assist in efficiently providingthe appropriate resources and quality of service to both roaming andnon-roaming mobile devices. By implementing the present disclosure, theuser experience may be improved. Set forth below are further exemplarysystems, devices, and components in which aspects of intelligent roamingand interworking may be implemented.

FIG. 9 illustrates an example wireless device 1010 that may be used inconnection with an embodiment. References will also be made to otherfigures of the present disclosure as appropriate. For example, mobiledevices 210, 310, and/or 610 may be wireless devices of the typedescribed in regard to FIG. 9, and may have some, all, or none of thecomponents and modules described in regard to FIG. 9. It will beappreciated that the components and modules of wireless device 1010illustrated in FIG. 9 are illustrative, and that any number and type ofcomponents and/or modules may be present in wireless device 1010. Inaddition, the functions performed by any or all of the components andmodules illustrated in FIG. 9 may be performed by any number of physicalcomponents. Thus, it is possible that in some embodiments thefunctionality of more than one component and/or module illustrated inFIG. 9 may be performed by any number or types of hardware and/orsoftware.

Processor 1021 may be any type of circuitry that performs operations onbehalf of wireless device 1010. In one embodiment, processor 1021executes software (i.e., computer readable instructions stored in acomputer readable medium) that may include functionality related toefficient processing of radio resource requests, for example. Userinterface module 1022 may be any type or combination of hardware and/orsoftware that enables a user to operate and interact with wirelessdevice 1010, and, in one embodiment, to interact with a system orsoftware enabling the user to place, request, and/or receive calls, textcommunications of any type, voicemail, voicemail notifications,voicemail content and/or data, and/or a system or software enabling theuser to view, modify, or delete related software objects. For example,user interface module 1022 may include a display, physical and/or “soft”keys, voice recognition software, a microphone, a speaker and the like.Wireless communication module 1023 may be any type of transceiverincluding any combination of hardware and/or software that enableswireless device 1010 to communicate with wireless network equipment.Memory 1024 enables wireless device 1010 to store information, such asAPNs, MNCs, MCCs, text communications content and associated data,multimedia content, software to efficiently process radio resourcerequests, and radio resource request processing preferences andconfigurations. Memory 1024 may take any form, such as internal randomaccess memory (RAM), an SD card, a microSD card and the like. Powersupply 1025 may be a battery or other type of power input (e.g., acharging cable that is connected to an electrical outlet, etc.) that iscapable of powering wireless device 1010. SIM 1026 may be any typeSubscriber Identity Module and may be configured on a removable ornon-removable SIM card that allows wireless device 1010 to store data onSIM 1026.

FIG. 10 is a block diagram of an example processor 1158 which may beemployed in any of the embodiments described herein, including as one ormore components of mobile devices 210, 310, and 610, as one or morecomponents of network equipment or related equipment, and/or as one ormore components of any third party system or subsystem that mayimplement any portion of the subject matter described herein. It isemphasized that the block diagram depicted in FIG. 10 is exemplary andnot intended to imply a specific implementation. Thus, the processor1158 can be implemented in a single processor or multiple processors.Multiple processors can be distributed or centrally located. Multipleprocessors can communicate wirelessly, via hard wire, or a combinationthereof.

As depicted in FIG. 10, the processor 1158 comprises a processingportion 1160, a memory portion 1162, and an input/output portion 1164.The processing portion 1160, memory portion 1162, and input/outputportion 1164 are coupled together (coupling not shown in FIG. 10) toallow communications between these portions. The input/output portion1164 is capable of providing and/or receiving components, commands,and/or instructions, utilized to, for example, request and receive APNs,MNCs, and/or MCCs, establish and terminate communications sessions,transmit and receive data access request data and responses, transmit,receive, store and process text, data, and voice communications, executesoftware that efficiently processes radio resource requests, receive andstore radio resource requests, radio resource request processingpreferences and configurations, and/or perform any other functiondescribed herein.

The processor 1158 may be implemented as a client processor and/or aserver processor. In a basic configuration, the processor 1158 mayinclude at least one processing portion 1160 and memory portion 1162.The memory portion 1162 can store any information utilized inconjunction with establishing, transmitting, receiving, and/orprocessing text, data, and/or voice communications,communications-related data and/or content, voice calls, othertelephonic communications, etc. For example, the memory portion iscapable of storing APNs, MNCs, MCCs, radio resource requests, softwarefor an efficient radio resource request processing system, text and datacommunications, calls, voicemail, multimedia content, visual voicemailapplications, etc. Depending upon the exact configuration and type ofprocessor, the memory portion 1162 can be volatile (such as RAM) 1166,non-volatile (such as ROM, flash memory, etc.) 1168, or a combinationthereof. The processor 1158 can have additional features/functionality.For example, the processor 1158 can include additional storage(removable storage 1170 and/or non-removable storage 1172) including,but not limited to, magnetic or optical disks, tape, flash, smart cardsor a combination thereof. Computer storage media, such as memory andstorage elements 1162, 1170, 1172, 1166, and 1168, may include volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules, or other data.Computer storage media include, but are not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,universal serial bus (USB) compatible memory, smart cards, or any othermedium that can be used to store the desired information and that can beaccessed by the processor 1158. Any such computer storage media may bepart of the processor 1158.

The processor 1158 may also contain the communications connection(s)1180 that allow the processor 1158 to communicate with other devices,for example through a radio access network (RAN). Communicationsconnection(s) 1180 is an example of communication media. Communicationmedia typically embody computer-readable instructions, data structures,program modules or other data in a modulated data signal such as acarrier wave or other transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection as might be used with a land line telephone, andwireless media such as acoustic, RF, infrared, cellular, and otherwireless media. The term computer-readable media as used herein includesboth storage media and communication media. The processor 1158 also canhave input device(s) 1176 such as keyboard, keypad, mouse, pen, voiceinput device, touch input device, etc. Output device(s) 1174 such as adisplay, speakers, printer, etc. also can be included.

A RAN as described herein may comprise any telephony radio network, orany other type of communications network, wireline or wireless, or anycombination thereof. The following description sets forth some exemplarytelephony radio networks, such as the global system for mobilecommunications (GSM), and non-limiting operating environments. Thebelow-described operating environments should be considerednon-exhaustive, however, and thus the below-described networkarchitectures merely show how intelligent roaming and interworking maybe implemented with stationary and non-stationary network structures andarchitectures in order to provide efficient processing of radio resourcerequests. It can be appreciated, however, that intelligent roaming andinterworking as described herein may be incorporated with existingand/or future alternative architectures for communication networks aswell.

The GSM is one of the most widely utilized wireless access systems intoday's fast growing communication environment. The GSM providescircuit-switched data services to subscribers, such as mobile telephoneor computer users. The General Packet Radio Service (GPRS), which is anextension to GSM technology, introduces packet switching to GSMnetworks. The GPRS uses a packet-based wireless communication technologyto transfer high and low speed data and signaling in an efficientmanner. The GPRS attempts to optimize the use of network and radioresources, thus enabling the cost effective and efficient use of GSMnetwork resources for packet mode applications.

The exemplary GSM/GPRS environment and services described herein alsomay be extended to 3G services, such as Universal Mobile TelephoneSystem (UMTS), Frequency Division Duplexing (FDD) and Time DivisionDuplexing (TDD), High Speed Packet Data Access (HSPDA), cdma2000 1xEvolution Data Optimized (EVDO), Code Division Multiple Access-2000(cdma2000 3x), Time Division Synchronous Code Division Multiple Access(TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), EnhancedData GSM Environment (EDGE), International MobileTelecommunications-2000 (IMT-2000), Digital Enhanced CordlessTelecommunications (DECT), 4G Services such as Long Term Evolution(LTE), etc., as well as to other network services that become availablein time. In this regard, intelligent roaming and interworking may beapplied independently of the method of data transport, and does notdepend on any particular network architecture, or underlying protocols.

FIG. 11 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichintelligent roaming and interworking systems and methods such as thosedescribed herein may be practiced. In an example configuration, any RANas described herein may be encompassed by or interact with the networkenvironment depicted in FIG. 11. Similarly, mobile devices 210, 310, and610 may communicate or interact with a network environment such as thatdepicted in FIG. 11. In such an environment, there may be a plurality ofBase Station Subsystems (BSS) 900 (only one is shown), each of whichcomprises a Base Station Controller (BSC) 902 serving a plurality ofBase Transceiver Stations (BTS) such as BTSs 904, 906, and 908. BTSs904, 906, 908, etc. are the access points where users of packet-basedmobile devices (e.g., mobile devices 210, 310, and 610) become connectedto the wireless network. In exemplary fashion, the packet trafficoriginating from user devices (e.g., mobile devices 210, 310, and 610)may be transported via an over-the-air interface to a BTS 908, and fromthe BTS 908 to the BSC 902. Base station subsystems, such as BSS 900,may be a part of internal frame relay network 910 that can includeService GPRS Support Nodes (SGSN) such as SGSN 912 and 914. Each SGSNmay be connected to an internal packet network 920 through which a SGSN912, 914, etc. may route data packets to and from a plurality of gatewayGPRS support nodes (GGSN) 922, 924, 926, etc. As illustrated, SGSN 914and GGSNs 922, 924, and 926 may be part of internal packet network 920.Gateway GPRS serving nodes 922, 924 and 926 may provide an interface toexternal Internet Protocol (IP) networks, such as Public Land MobileNetwork (PLMN) 950, corporate intranets 940, or Fixed-End System (FES)or the public Internet 930. As illustrated, subscriber corporate network940 may be connected to GGSN 924 via firewall 932, and PLMN 950 may beconnected to GGSN 924 via border gateway router 934. The RemoteAuthentication Dial-In User Service (RADIUS) server 942 may be used forcaller authentication when a user of a mobile cellular device callscorporate network 940.

Generally, there can be four different cell sizes in a GSM network,referred to as macro, micro, pico, and umbrella cells. The coverage areaof each cell is different in different environments. Macro cells may beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells may betypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells may be used mainly indoors.On the other hand, umbrella cells may be used to cover shadowed regionsof smaller cells and fill in gaps in coverage between those cells.

FIG. 12 illustrates an architecture of a typical GPRS network segmentedinto four groups: users 1050, radio access network 1060, core network1070, and interconnect network 1080. Users 1050 may comprise a pluralityof end users (though only mobile subscriber 1055 is shown in FIG. 12).In an example embodiment, the device depicted as mobile subscriber 1055may comprise any of mobile devices 210, 310, and 610. Radio accessnetwork 1060 comprises a plurality of base station subsystems such asBSSs 1062, which include BTSs 1064 and BSCs 1066. Core network 1070comprises a host of various network elements. As illustrated here, corenetwork 1070 may comprise Mobile Switching Center (MSC) 1071, ServiceControl Point (SCP) 1072, gateway MSC 1073, SGSN 1076, Home LocationRegister (HLR) 1074, Authentication Center (AuC) 1075, Domain NameServer (DNS) 1077, and GGSN 1078. Interconnect network 1080 may alsocomprise a host of various networks and other network elements. Asillustrated in FIG. 12, interconnect network 1080 comprises PublicSwitched Telephone Network (PSTN) 1082, Fixed-End System (FES) orInternet 1084, firewall 1088, and Corporate Network 1089.

A mobile switching center may be connected to a large number of basestation controllers. At MSC 1071, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (PSTN) 1082 through Gateway MSC (GMSC)1073, and/or data may be sent to SGSN 1076 that may send the datatraffic to GGSN 1078 for further forwarding.

When MSC 1071 receives call traffic, for example, from BSC 1066, it maysend a query to a database hosted by SCP 1072. The SCP 1072 may processthe request and may issue a response to MSC 1071 so that it may continuecall processing as appropriate.

The HLR 1074 may be a centralized database for users to register to theGPRS network. HLR 1074 may store static information about thesubscribers such as the International Mobile Subscriber Identity (IMSI),APN profiles as described herein, subscribed services, and a key forauthenticating the subscriber. HLR 1074 may also store dynamicsubscriber information such as dynamic APN profiles as describe hereinand the current location of the mobile subscriber. HLR 1074 may alsoserve to intercept and determine the validity of destination numbers inmessages sent from a device, such as mobile subscriber 1055, asdescribed herein. Associated with HLR 1074 may be AuC 1075. AuC 1075 maybe a database that contains the algorithms for authenticatingsubscribers and may include the associated keys for encryption tosafeguard the user input for authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as mobile devices 210, 310, and 610, used by an end user ofa mobile cellular service or a wireless provider. When a mobilesubscriber turns on his or her mobile device, the mobile device may gothrough an attach process by which the mobile device attaches to an SGSNof the GPRS network. In FIG. 12, when mobile subscriber 1055 initiatesthe attach process by turning on the network capabilities of the mobiledevice, an attach request may be sent by mobile subscriber 1055 to SGSN1076. The SGSN 1076 queries another SGSN, to which mobile subscriber1055 was attached before, for the identity of mobile subscriber 1055.Upon receiving the identity of mobile subscriber 1055 from the otherSGSN, SGSN 1076 may request more information from mobile subscriber1055. This information may be used to authenticate mobile subscriber1055 to SGSN 1076 by HLR 1074. Once verified, SGSN 1076 sends a locationupdate to HLR 1074 indicating the change of location to a new SGSN, inthis case SGSN 1076. HLR 1074 may notify the old SGSN, to which mobilesubscriber 1055 was attached before, to cancel the location process formobile subscriber 1055. HLR 1074 may then notify SGSN 1076 that thelocation update has been performed. At this time, SGSN 1076 sends anAttach Accept message to mobile subscriber 1055, which in turn sends anAttach Complete message to SGSN 1076.

After attaching itself with the network, mobile subscriber 1055 may thengo through the authentication process. In the authentication process,SGSN 1076 may send the authentication information to HLR 1074, which maysend information back to SGSN 1076 based on the user profile that waspart of the user's initial setup. The SGSN 1076 may then send a requestfor authentication and ciphering to mobile subscriber 1055. The mobilesubscriber 1055 may use an algorithm to send the user identification(ID) and password to SGSN 1076. The SGSN 1076 may use the same algorithmand compares the result. If a match occurs, SGSN 1076 authenticatesmobile subscriber 1055.

Next, the mobile subscriber 1055 may establish a user session with thedestination network, corporate network 1089, by going through a PacketData Protocol (PDP) activation process. Briefly, in the process, mobilesubscriber 1055 may request access to the Access Point Name (APN), forexample, UPS.com, and SGSN 1076 may receive the activation request frommobile subscriber 1055. SGSN 1076 may then initiate a Domain NameService (DNS) query to learn which GGSN node has access to the UPS.comAPN. The DNS query may be sent to the DNS server within the core network1070, such as DNS 1077, which may be provisioned to map to one or moreGGSN nodes in the core network 1070. Based on the APN, the mapped GGSN1078 can access the requested corporate network 1089. The SGSN 1076 maythen send to GGSN 1078 a Create Packet Data Protocol (PDP) ContextRequest message that contains necessary information. The GGSN 1078 maysend a Create PDP Context Response message to SGSN 1076, which may thensend an Activate PDP Context Accept message to mobile subscriber 1055.

Once activated, data packets of the call made by mobile subscriber 1055may then go through radio access network 1060, core network 1070, andinterconnect network 1080, in a particular fixed-end system, or Internet1084 and firewall 1088, to reach corporate network 1089.

Thus, network elements that can invoke the functionality of intelligentroaming and interworking systems and methods such as those describedherein may include, but are not limited to, Gateway GPRS Support Nodetables, Fixed End System router tables, firewall systems, VPN tunnels,and any number of other network elements as required by the particulardigital network.

FIG. 13 illustrates another exemplary block diagram view of aGSM/GPRS/IP multimedia network architecture 1100 in which the systemsand methods for intelligent roaming and interworking such as thosedescribed herein may be incorporated. As illustrated, architecture 1100of FIG. 13 includes a GSM core network 1101, a GPRS network 1130 and anIP multimedia network 1138. The GSM core network 1101 includes a MobileStation (MS) 1102, at least one Base Transceiver Station (BTS) 1104 anda Base Station Controller (BSC) 1106. The MS 1102 is physical equipmentor Mobile Equipment (ME), such as a mobile telephone or a laptopcomputer (e.g., mobile devices 210, 310, and 610) that is used by mobilesubscribers, in one embodiment with a Subscriber identity Module (SIM).The SIM includes an International Mobile Subscriber Identity (IMSI),which is a unique identifier of a subscriber. The SIM may also includeAPNs, such as a PHONE APN and a ROAM APN as described herein. The BTS1104 may be physical equipment, such as a radio tower, that enables aradio interface to communicate with the MS. Each BTS may serve more thanone MS. The BSC 1106 may manage radio resources, including the BTS. TheBSC may be connected to several BTSs. The BSC and BTS components, incombination, are generally referred to as a base station (BSS) or radioaccess network (RAN) 1103.

The GSM core network 1101 may also include a Mobile Switching Center(MSC) 1108, a Gateway Mobile Switching Center (GMSC) 1110, a HomeLocation Register (HLR) 1112, Visitor Location Register (VLR) 1114, anAuthentication Center (AuC) 1118, and an Equipment Identity Register(EIR) 1116. The MSC 1108 may perform a switching function for thenetwork. The MSC may also perform other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1110 may provide a gateway between the GSM network and other networks,such as an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1120. Thus, the GMSC 1110 providesinterworking functionality with external networks.

The HLR 1112 may be a database that may contain administrativeinformation regarding each subscriber registered in a corresponding GSMnetwork. Such information may include APNs and APN profiles as describedherein. The HLR 1112 may also contain the current location of each MS.The VLR 1114 may be a database that contains selected administrativeinformation from the HLR 1112. The VLR may contain information necessaryfor call control and provision of subscribed services for each MScurrently located in a geographical area controlled by the VLR. The HLR1112 and the VLR 1114, together with the MSC 1108, may provide the callrouting and roaming capabilities of GSM. The AuC 1116 may provide theparameters needed for authentication and encryption functions. Suchparameters allow verification of a subscriber's identity. The EIR 1118may store security-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1109 allows one-to-one shortmessage service (SMS), or multimedia message service (MMS), messages tobe sent to/from the MS 1102. A Push Proxy Gateway (PPG) 1111 is used to“push” (i.e., send without a synchronous request) content to the MS1102. The PPG 1111 acts as a proxy between wired and wireless networksto facilitate pushing of data to the MS 1102. A Short Message Peer toPeer (SMPP) protocol router 1113 may be provided to convert SMS-basedSMPP messages to cell broadcast messages. SMPP is a protocol forexchanging SMS messages between SMS peer entities such as short messageservice centers. The SMPP protocol is often used to allow third parties,e.g., content suppliers such as news organizations, to submit bulkmessages.

To gain access to GSM services, such as voice, data, short messageservice (SMS), and multimedia message service (MMS), the MS may firstregister with the network to indicate its current location by performinga location update and IMSI attach procedure. MS 1102 may send a locationupdate including its current location information to the MSC/VLR, viaBTS 1104 and BSC 1106. The location information may then be sent to theMS's HLR. The HLR may be updated with the location information receivedfrom the MSC/VLR. The location update may also be performed when the MSmoves to a new location area. Typically, the location update may beperiodically performed to update the database as location updatingevents occur.

GPRS network 1130 may be logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1132, a cell broadcast and a GatewayGPRS support node (GGSN) 1134. The SGSN 1132 may be at the samehierarchical level as the MSC 1108 in the GSM network. The SGSN maycontrol the connection between the GPRS network and the MS 1102. TheSGSN may also keep track of individual MS's locations and securityfunctions and access controls.

Cell Broadcast Center (CBC) 1133 may communicate cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile telephone customers whoare located within a given part of its network coverage area at the timethe message is broadcast.

GGSN 1134 may provide a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1136. That is, the GGSN mayprovide interworking functionality with external networks, and set up alogical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it may be transferred to an external TCP-IPnetwork 1136, such as an X.25 network or the Internet. In order toaccess GPRS services, the MS first attaches itself to the GPRS networkby performing an attach procedure. The MS then activates a packet dataprotocol (PDP) context, thus activating a packet communication sessionbetween the MS, the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services may be used inparallel. The MS may operate in one three classes: class A, class B, andclass C. A class A MS may attach to the network for both GPRS servicesand GSM services simultaneously. A class A MS may also supportsimultaneous operation of GPRS services and GSM services. For example,class A mobiles may receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS may attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

GPRS network 1130 may be designed to operate in three network operationmodes (NOM1, NOM2 and NOM3). A network operation mode of a GPRS networkmay be indicated by a parameter in system information messagestransmitted within a cell. The system information messages may direct anMS where to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS may receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS maysuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS may bereceiving data and may not be listening to a paging channel. In a NOM3network, a MS may monitor pages for a circuit switched network whilereceiving data and vice versa.

The IP multimedia network 1138 was introduced with 3GPP Release 5, andmay include IP multimedia subsystem (IMS) 1140 to provide richmultimedia services to end users. A representative set of the networkentities within IMS 1140 are a call/session control function (CSCF), amedia gateway control function (MGCF) 1146, a media gateway (MGW) 1148,and a master subscriber database, called a home subscriber server (HSS)1150. HSS 1150 may be common to GSM core network 1101, GPRS network 1130as well as IP multimedia network 1138.

IP multimedia system 1140 may be built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1143, a proxy CSCF (P-CSCF) 1142, and a serving CSCF (S-CSCF) 1144. TheP-CSCF 1142 is the MS's first point of contact with the IMS 1140. TheP-CSCF 1142 may forward session initiation protocol (SIP) messagesreceived from the MS to an SIP server in a home network (and vice versa)of the MS. The P-CSCF 1142 may also modify an outgoing request accordingto a set of rules defined by the network operator (for example, addressanalysis and potential modification).

I-CSCF 1143 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. I-CSCF 1143 may contact subscriberlocation function (SLF) 1145 to determine which HSS 1150 to use for theparticular subscriber, if multiple HSSs 1150 are present. S-CSCF 1144may perform the session control services for MS 1102. This includesrouting originating sessions to external networks and routingterminating sessions to visited networks. S-CSCF 1144 may also decidewhether an application server (AS) 1152 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromHSS 1150 (or other sources, such as application server 1152). AS 1152may also communicate to location server 1156 (e.g., a Gateway MobileLocation Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of MS 1102.

HSS 1150 may contain a subscriber profile and keep track of which corenetwork node is currently handling the subscriber. It may also supportsubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1150, a subscriber location function providesinformation on the HSS 1150 that contains the profile of a givensubscriber.

MGCF 1146 may provide interworking functionality between SIP sessioncontrol signaling from the IMS 1140 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown.) It may also control themedia gateway (MGW) 1148 that provides user-plane interworkingfunctionality (e.g., converting between AMR- and PCM-coded voice.) MGW1148 may also communicate with other IP multimedia networks 1154.

Push to Talk over Cellular (PoC) capable mobile telephones may registerwith the wireless network when the telephones are in a predefined area(e.g., job site, etc.) When the mobile telephones leave the area, theymay register with the network in their new location as being outside thepredefined area. This registration, however, does not indicate theactual physical location of the mobile telephones outside thepre-defined area.

While example embodiments of systems and methods intelligent roaming andinterworking have been described in connection with variouscommunications devices and computing devices/processors, the underlyingconcepts can be applied to any communications or computing device,processor, or system capable of implementing the intelligent roaming andinterworking systems and methods described. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and apparatuses for intelligent roaming and interworking, orcertain aspects or portions thereof, can take the form of program code(i.e., instructions) embodied in tangible and/or non-transitory media,such as floppy diskettes, CD-ROMs, hard drives, or any othermachine-readable storage medium, wherein, when the program code isloaded into and executed by a machine, such as a computer, the machinebecomes an apparatus for intelligent roaming and interworking. In thecase of program code execution on programmable computers, the computingdevice will generally include a processor, a storage medium readable bythe processor (including volatile and non-volatile memory and/or storageelements), at least one input device, and at least one output device.The program(s) can be implemented in assembly or machine language, ifdesired. The language can be a compiled or interpreted language, andcombined with hardware implementations.

Methods and systems for intelligent roaming and interworking may also bepracticed via communications embodied in the form of program code thatis transmitted over some transmission medium, such as over electricalwiring or cabling, through fiber optics, or via any other form oftransmission, wherein, when the program code is received, loaded into,and executed by a machine, such as an EPROM, a gate array, aprogrammable logic device (PLD), a client computer, or the like, themachine becomes an apparatus for intelligent roaming and interworking.When implemented on a general-purpose processor, the program codecombines with the processor to provide a unique apparatus that operatesto invoke the functionality of intelligent roaming and interworking asdescribed herein. Additionally, any storage techniques used inconnection with an intelligent roaming and interworking system mayinvariably be a combination of hardware and software.

While intelligent roaming and interworking systems and methods have beendescribed in connection with the various embodiments of the variousfigures, it is to be understood that other similar embodiments may beused or modifications and additions may be made to the describedembodiments for performing the same function of intelligent roaming andinterworking without deviating therefrom. For example, one skilled inthe art will recognize that intelligent roaming and interworking asdescribed in the present application may apply to any environment,whether wired or wireless, and may be applied to any number of suchdevices connected via a communications network and interacting acrossthe network. Therefore, intelligent roaming and interworking should notbe limited to any single embodiment, but rather should be construed inbreadth and scope in accordance with the appended claims.

What is claimed:
 1. A method comprising: receiving a query on a mobiledevice; transmitting a network code from the mobile device; receiving anindication of roaming status on the mobile device; selecting an accesspoint name from a plurality of access point names based on theindication of roaming status; and transmitting a service requestcomprising the access point name from the mobile device.
 2. The methodof claim 1, wherein the network code comprises a mobile network code anda mobile country code.
 3. The method of claim 1, further comprisingreceiving a confirmation that that the mobile device is eligible to usethe wireless network.
 4. The method of claim 1, wherein selecting theaccess point name comprises determining from the indication of roamingstatus that the mobile device is roaming, and, in response, selecting aroaming access point name.
 5. The method of claim 1, wherein selectingthe access point name comprises determining from the indication ofroaming status that the mobile device is not roaming, and, in response,selecting a non-roaming access point name.
 6. The method of claim 1,further comprising establishing a bearer path with the wireless network.7. A network device comprising: a transceiver configured to: transmit aquery requesting mobile device identifying information; receive mobiledevice identifying information; transmit a roaming status; and receive aservice request comprising an access point name; a processor configuredto: determine the roaming status based on the mobile device identifyinginformation; determine service parameters based on the access pointname; and establish a communications link based on the serviceparameters.
 8. The network device of claim 7, wherein the transceiver isconfigured to receive the mobile device identifying information byreceiving a mobile network code and a mobile country code.
 9. Thenetwork device of claim 7, wherein the processor is configured todetermine the service parameters by transmitting a query comprising theaccess point name to a home location register.
 10. The network device ofclaim 9, wherein the home location register and the network device arewithin a first network.
 11. The network device of claim 10, wherein thequery causes the home location register in the first network to query asecond home location register in a second network.
 12. The networkdevice of claim 9, wherein the home location register is in a firstnetwork and the network device is in a second network.
 13. The networkdevice of claim 7, wherein the transceiver is further configured toreceive the service parameters from a home location register.
 14. Thenetwork device of claim 7, wherein the service parameters comprisequality of service parameters.
 15. A system comprising at least oneprocessor configured to: receive a request for service parameters, therequest comprising an access point name; determine an access point nameprofile based on the access point name; retrieve the service parametersfrom the access point name profile; and transmit the service parameters.16. The system of claim 15, wherein the access point name profile isdetermined by querying a local database.
 17. The system of claim 15,wherein the system is located in a first network, and wherein the accesspoint name profile is determined by transmitting a query to a homelocation register located in a second network and receiving the accesspoint name profile from the home location register.
 18. The system ofclaim 17, wherein the at least one processor is further configured tostore the access point name profile in a local database.
 19. The systemof claim 18, wherein the at least one processor is further configuredto: receive a second request for second service parameters comprisingthe access point name; and determine the access point name profile basedon the access point name by querying the local database.
 20. The systemof claim 15, wherein the system is located in a first network, andwherein the request for service parameters is received from a homelocation register located in a second network.